Add CLA Assistant retry workflow#5234
Open
clockwork-labs-bot wants to merge 8 commits into
Open
Conversation
clockwork-labs-bot
requested review from
bfops,
cloutiertyler and
jdetter
as code owners
clockwork-labs-bot
force-pushed
the
bot/retry-cla-assistant
branch
3 times, most recently
from
1bbbd39 to
dde5524
Compare
bfops
reviewed
Jun 4, 2026
bfops
reviewed
Jun 4, 2026
clockwork-labs-bot
force-pushed
the
bot/retry-cla-assistant
branch
from
dde5524 to
5a5a560
Compare
bfops
reviewed
Jun 4, 2026
Signed-off-by: Zeke Foppa <196249+bfops@users.noreply.github.com>
Signed-off-by: Zeke Foppa <196249+bfops@users.noreply.github.com>
Signed-off-by: Zeke Foppa <196249+bfops@users.noreply.github.com>
bfops
reviewed
Jun 4, 2026
| - name: Recheck CLA Assistant | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| INPUT_PR_NUMBER: ${{ inputs.pr_number }} |
bfops
reviewed
Jun 4, 2026
| } | ||
| } | ||
|
|
||
| let event_name = env::var("GITHUB_EVENT_NAME").unwrap_or_default(); |
Collaborator
There was a problem hiding this comment.
I think this github-workflow-specific logic should be moved into the github workflow. the conclusion should be passed in via the --pr-number arg (which should now be required)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Retry CLA Assistantworkflow for cases wherelicense/clais missing or pending after the normal PR checks have gone green.cargo ci retry-cla-assistant --pr-number <number>.tools/cicrate.Behavior
The workflow passes explicit PR numbers into the Rust command. For scheduled runs, it enumerates open
masterPRs in the workflow and invokes the Rust command for each one.The
cargo ci retry-cla-assistant --pr-number <number>command only calls CLA Assistant's recheck endpoint when the PR is open, non-draft, targetsmaster, the head SHA is at least 10 minutes old, at least one check run exists, all reported check runs are green, no non-CLA commit status is non-green, andlicense/clais missing/pending/failing.The
workflow_runtrigger is intentionally unfiltered, so adding or renaming CI workflows does not require changing this workflow.It calls
https://cla-assistant.io/check/{owner}/{repo}?pullRequest={number}and pollslicense/clafor up to 3 minutes.Safety
pull_request_target, but it does not check out or execute PR code. It checks out the trusted default branch before running the CI tool.Retry CLA Assistantworkflow itself.license/clastatus.Validation
cargo fmt --package ci.cargo check -p ci.cargo ci retry-cla-assistant --helpand verified--pr-numberis required.unstablefeature #5164 metadata and caught that a hard-coded required-check list was too strict; replaced that list with a reported-checks-all-green gate.Addresses #5215.